-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing one nat rule restriction in a nat rule collection - Firewall Policy[DO NOT MERGE] #9246
Closed
saisujithreddym
wants to merge
1
commit into
Azure:network-april-release
from
saisujithreddym:network-april-release2
Closed
Removing one nat rule restriction in a nat rule collection - Firewall Policy[DO NOT MERGE] #9246
saisujithreddym
wants to merge
1
commit into
Azure:network-april-release
from
saisujithreddym:network-april-release2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
saisujithreddym
requested review from
MikhailTryakhov,
anton-evseev and
v-shhatt
as code owners
April 27, 2020 20:28
Azure Pipelines successfully started running 1 pipeline(s). |
saisujithreddym
changed the title
Removing one nat rule restriction in a nat rule collection
Removing one nat rule restriction in a nat rule collection - Firewall Policy
Apr 27, 2020
azure-sdk-for-go
|
azure-cli-extensions
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-java
|
azure-sdk-for-js
|
Can one of the admins verify this patch? |
openapi-assignment-bot
bot
added
the
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
label
Apr 28, 2020
lirenhe
approved these changes
Apr 29, 2020
saisujithreddym
changed the title
Removing one nat rule restriction in a nat rule collection - Firewall Policy
Removing one nat rule restriction in a nat rule collection - Firewall Policy[DO NOT MERGE]
Apr 29, 2020
anton-evseev
added
the
DoNotMerge
<valid label in PR review process> use to hold merge after approval
label
May 4, 2020
I will make this PR against the may release branch. Closing this for now |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
DoNotMerge
<valid label in PR review process> use to hold merge after approval
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.